Change Management: The Core Task of Ontology Versioning and Evolution

Change management as a key issue in ontology versioning and evolution is still not fully addressed, which to some extent forms a barrier against the smooth process of ontology evolution. The key issue in the support of evolving ontologies is to distinguish and recognize the changes during the process of ontology evolution. Most of the current popular work on ontology versioning do not keep a record of the changes in the ontology, thus preventing the user from tracking those changes back and forward, or to at least understand the rational behind those changes. We are proposing an approach to get the evidences of ontology changes, keep track of them, and manage them in an engineering fashion

Ontology Change Management in Protégé

Ontology schemas tend to change and evolve over time to meet new requirements. This change may invalidate dependent applications if there is no dynamic adaptation to the changes made to underlying ontologies. Protégé, as a popular ontology development tool, should meet the challenges addressed by the evolving ontology. In this paper, we will briefly analyse the current ontology-change management in Protégé, and propose some extensions to facilitate change traceability by external application and services

Ontologies Change and Queries Break: Towards a Solution

Keeping track of ontology changes is becoming a critical issue for ontology-based applications. Updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of mapping ontology versions and keeping consistent with the instances. Very little work investigated controlling the impact on dependent applications/services; which is the aim of the system presented in this paper. The approach we propose is to make use of ontology change logs to analyse incoming RDQL queries and amend them as necessary. Revised queries can then be used to query the ontology and knowledge base as requested by the applications and services. We describe the design of our prototype system, and discuss related problems and future directions

Ontology Change Management in Protégé

Ontology schemas tend to change and evolve over time to meet new requirements. This change may invalidate dependent applications if there is no dynamic adaptation to the changes made to underlying ontologies. Protégé, as a popular ontology development tool, should meet the challenges addressed by the evolving ontology. In this paper, we will briefly analyse the current ontology-change management in Protégé, and propose some extensions to facilitate change traceability by external application and services

An Approach to Cope with Ontology Changes for Ontology-based Applications

Keeping track of ontology changes is becoming a critical issue for ontology-based applications because updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and dependent applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of the attempts to ease the communications between ontology versions and keep consistent with the instances, and there is little work available on controlling the impact to dependent applications/services which is the aims of the system presented in this paper. The approach we propose in this paper is to manually capture and log ontology changes, use this log to analyse incoming RDQL queries and amend them as necessary. Revised queries can then be used to query the knowledge base of the applications/services. We present the infrastructure of our approach based on the problems and scenarios identified within ontology-based systems. We discuss the issues met during our design and implementation, and consider some problems whose solutions will be beneficial to the development of our approach

A one-dimensional extremely covalent material: monatomic carbon linear chain

Polyyne and cumulene of infinite length as the typical covalent one-dimensional (1D) monatomic linear chains of carbon have been demonstrated to be metallic and semiconductor (Eg = 1.859 eV), respectively, by first-principles calculations. Comparing with single-walled carbon nanotubes, the densities are evidently low and the thermodynamic properties are similar below room temperature but much different at the high temperature range. Polyyne possesses a Young's modulus as high as 1.304 TPa, which means it is even much stiffer than carbon nanotubes and to be the superlative strong 1D material along the axial direction. The Young's modulus of cumulene is estimated to be 760.78 GPa. In addition, polyyne is predicted to be as a one-dimensional electronic material with very high mobility

Changing Ontology Breaks the Queries

Updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of mapping ontology versions and keeping consistent with the instances. Very little work investigated controlling the impact on dependent applications/services; which is the aim of the system presented in this paper. The approach we propose is to make use of ontology change logs to analyse incoming RDQL queries and amend them as necessary. Revised queries can then be used to query the ontology and knowledge base as requested by the applications and services. We describe our prototype system and discuss related problems and future directions

Enabling Active Ontology Change Management within Semantic Web-based Applications. Mini-thesis: PhD upgrade report

Enabling traceable ontology changes is becoming a critical issue for ontology-based applications. Updating an ontology that is in use may result in inconsistencies between the ontology and the knowledge base, dependent ontologies and applications/services. Current research concentrates on the creation of ontologies and how to manage ontology changes in terms of mapping ontology versions and keeping consistent with the instances. Very little work investigated on-the-fly keeping track of ontology changes while update (active ontology versioning) and using these information to control the impact on dependent applications/services, which is the aim of our research presented in this thesis. The approach we propose is to make use of ontology change logs as a check-point to analyse changed entities related to the requested services via end-user’s incoming queries (RDQL/SPARQL) and amend them as necessary to maintain the validation and continuousness of the dependent application. Firstly, We build up Log Ontology I as the concept structure to organize and construct the change information, develop our prototype system to demonstrate how the change information retrieved from Log Ontology I could be used to control the impacts brought by the ontology changes on the dependent applications and services. And then, by analysing the limitations and difficulties of our prototype system in maintaining the services related to the more complex ontology changes, we identify that the problem which fails the system facing the more complex ontology changes is the inabilities of Log Ontology I to represent complex change information in a semantic fashion. Therefore, we retract to put more focuses on Log Ontology I to enable the implementation of the mechanism to on-the-fly keep track of ontology change information, forming Log Ontology II, in order to reserve the semantics of ontology change from the beginning of ontology update process. Finally we discuss the future direction in terms of how the improved Log Ontology II enables the better service validation and continuousness maintenance of changing-ontology-based applications

Ontology Versioning and Evolution for Semantic Web-Based Applications. 9-month progress report

Successful Semantic Web-based applications not only need large amounts of underlying well-organised and well-interrelated ontologies to support their infrastructures, but also need to provide the end-users with the consistent and continuous services as usual while the underlying ontologies changing. Research on ontology versioning and evolution addresses the issues of how ontologies cope with the internal and external changing environment so as to keep ontologies consistent. The existing works on ontology versioning and evolution focus on the changes inside ontology itself, i.e., the relationships and interoperability of the various versions, and largely neglected the issue of how changes during ontology versioning and evolution could affect the existing applications/services. The potential research work presented in this report aims at addressing how we could apply ontology versioning and evolution technologies in the existing applications so as to enable applications to provide consistent and continuous services as usual by adapting to the newly updating underlying ontologies. In this report, a middle layer between the underlying ontologies and dependent applications is proposed to build, which is used to monitor and detect any changes performed on the important parts of an ontology specific for the applications, and divert queries accordingly. The framework and requirements of the middle layer are discussed, in addition to a review of progress to date and anticipated future work